How does IDS get a form effective date

Documaker Bridge rules expect the attachment variable ARCEFFECTIVEDATE in the format YYYYMMDD to specify the effective date of the transaction. Effective date is important if library manager is used to store versions of forms. Here is an example how this attachment variable can be passed in via a CGI interface when using the sample Documaker Bridge CGI retrieval pages.

When using Library manager with IDS, include the following attachment variable on the RECIPS.HTM page so IDS can compare the form’s effective date to the archived run date when you retrieve a form using Library manager.

 

lt;FORM METHOD=POST ACTION="#EXENAME,#">

lt;INPUT NAME="USERID" VALUE="#USERID,%s#" TYPE="HIDDEN">

lt;INPUT NAME="DOCTYPE" VALUE="#DOCTYPE,%s#" TYPE="HIDDEN">

lt;INPUT NAME="REQTYPE" VALUE="PRT" TYPE="HIDDEN">

lt;INPUT NAME="CONFIG" VALUE="#CONFIG,%s#" TYPE="HIDDEN">

lt;INPUT NAME="ARCKEY" VALUE="#ARCKEY,%s#" TYPE="HIDDEN">

lt;INPUT NAME="Company" VALUE="#Company,%s#" TYPE="HIDDEN">

lt;INPUT NAME="Lob" VALUE="#Lob,%s#" TYPE="HIDDEN">

lt;INPUT NAME="PolicyNum" VALUE="#PolicyNum,%s#" TYPE="HIDDEN">

lt;INPUT NAME="RunDate" VALUE="#RunDate,%s#" TYPE="HIDDEN">

lt;INPUT NAME="PRINTPATH" VALUE="#PRINTPATH,%s#" TYPE="HIDDEN">

lt;INPUT NAME="ARCEFFECTIVEDATE" VALUE="#RunDate,%s#" TYPE="HIDDEN">